We recommend that all AutoDoubler users upgrade to version 1.0.4 or later.
Instructions:
------------
The patcher by default patches the installed copy. It will only prompt you if it can't find the file to patch.
If you want to patch your master disk, follow these directions. Follow them carefully, or you may end up with a disk that won't install.
1. Throw the installed copy of AutoDoubler in the trash
2. Lock your original master disk.
3. Make a backup copy of your master disk (just in case). Remember to make the name of the backup disk exactly the same as the original disk name.
4. Copy just the AutoDoubler control panel from the master disk to your hard disk.
5. Run the patcher. It will prompt you for the file to patch. Select the AutoDoubler file on the hard disk.
5. Copy the now patched AutoDoubler back to the master disk.
6. Run the AutoDoubler installer on the master disk.
FIX LIST
--------
SALIENT SOFTWARE
18-Feb-92
MICROPHONE II, AD 1.0-1.0.2
MicroPhone will successfully send AD-compressed files over a modem, but it will send them twice. So the savings of sending a compressed file is nullified by sending the file twice. This conflict has been fixed in AD 1.0.3.
WORD 5.0, AD (all versions)
Word has a Find feature which directly parses the Apple file system's data structures. Those data structures are Apple private data which Apple may change at any time, causing Word 5.0 to break. As a result, Word will not Find compressed documents, unless you ask Word to find documents of any type. We consider this a bug in Word 5.0, so the Find command will not work until (unless) Microsoft fixes the problem.
DOUBLEUP COMPRESSION BOARD, AD (all versions), DD 3.7.2 (or later)
This is not a conflict. If a user does not have the DoubleUp board installed and attempts to expand a DoubleUp-compressed file using DD, an "Error 17" message will be generated. If AD attempts to open a DoubleUp file without the board present, AD will generate an error code -20992. DoubleUp must be installed to be able to open a DoubleUp file, so the error messages are correct. To avoid confusion, DD 3.7.4 has a more descriptive error message than "Error 17".
APPLESHARE, DD 3.7.2 or AD 1.0-1.0.2
This conflict only occurs under the following circumstances:
o AppleShare server machine running system 6.0.x
o Client machine running System 7 and either DD 3.7.2 or AD 1.0 (or both)
If the system 7 client attempts to compress files on the AppleShare server, the files will not get compressed. But their type will be changed to DD files. Any attempt to expand them will result in a "file corrupted" error message. The files are not corrupted, and they may be fixed by restoring the original type and creator of the file. This would be a major nuisance for a large number of files, so we consider this a major conflict. DD 3.7.3 and AD 1.0.3 fix the conflict.
TOPS, AD (all versions)
The conflict causes many different types of file error messages. No data corruption occurs with any of these errors. If users really want to run both TOPS and AD, make sure they load AD _after_ TOPS. We recommend our users migrate to another type of server software.
HANDOFF 2, FILESHARE, AD (all versions)
With these three items activated, a HandOff 2 bug is activated which causes a system freeze. Fred Hollander, author of HandOff 2, said that the bug will be fixed in the next revision of HandOff 2.
CLICK CHANGE, AD (all versions)
These two don't work together, causing system freezes in the Finder. We don't have a fix for this one at this time. Best thing to do is to turn off ClickChange. A user reported that loading AD after ClickChange seems to fix the conflict, but we have not yet verified this.
DISK EXPRESS 2, SYSTEM 6, AD 1.0-1.0.2
Running these two INITs under system 6 will result in a system error "unimplemented trap error" (system error 12), or a DiskExpress error code 2004. The problem occurs when Disk Express 2 calls a system 7 trap when running under system 6. AD 1.0.3 fixes this conflict.
NORTON FILESAVER, AD (all versions)
FileSaver will not work when Personal FileShare is turned on, no matter what other INITs are on. Norton will probably fix this some day. We recommend not running FileSaver, as it slows the computer down.
SAM, AFTER DARK, AD (all versions)
(See also the "Configuring Virus Checkers" document). This is not a conflict, but SAM can make it seem that After Dark has frozen. SAM will put up its warning alert when AD is compressing. The dialog will cause After Dark to APPEAR frozen. Hitting the enter key will get rid of the SAM dialog. Our suggestion: turn off After Dark while AutoDoubler is making its initial compression scan. Use SAM's "Learn" button when the SAM warnings come up. After SAM "learns" about AD, you can turn After Dark back on. NOTE: The same apparent "conflict" will occur with other screen savers and virus checkers, such as Pyro.
GATEKEEPER, AD (all versions)
(See also the "Configuring Virus Checkers" document). GateKeeper, a shareware virus protector, is very energetic at keeping things from happening to files. It won't allow AutoDoubler to perform background compression of many types of files. As a result, lots of temporary files will get scattered around the disk. These files start with "1.", "2.", etc. The solution is to stop using GateKeeper until GateKeeper gets fixed. AD 1.0.4 detects GateKeeper interference, displays an alert, and turns off automatic compression.
MPW, AD 1.0
MPW generates errors for certain compressed files it attempted to open. This conflict has been fixed with AD 1.0.1 and later.
M.Y.O.B., AD 1.0-1.0.2
Mind Your Own Business (MYOB) will generate I/O errors for certain files it attempts to open. This conflict has likely been fixed with AD 1.0.3.
DESKWRITER 2.2, DISKDOUBLER 3.7.2
With these two items installed, you will notice strangely shaded icons. Many icons will be shown as black rectangles. Also, when printing to the DeskWriter, an error -48 (duplicate filename) may result. The conflict has been resolved in DD 3.7.3.
FILEMAKER PRO, ANY FILE SERVER, DISKDOUBLER 3.7.2
This is a rather obscure conflict. The following conditions must be met to invoke the problem:
1) A FileMaker Pro database must be on a file server.
2) A DD-compressed file must reside in the same folder as the database.
3) A client who has DD 3.7.2 installed must try to open the database.
If all three of these conditions are met, the database will not be successully opened. The error message will say that the file is open or locked. DD 3.7.4 or later resolves the conflict. [NOTE: Other applications may have the same problem as FileMaker Pro, but that is the only one we know about at this time.]
PRINTMONITOR, AD 1.0-1.0.2
In some situations, PrintMonitor will generate an error message. The most common error message will contain the text "Where:80, Why:-50". The conflict is resolved with AD 1.0.3.
"PRINT DIRECTORY" COMMAND, System 6, AD 1.0-1.0.3
When using the Finder under System 6, choosing the "Print Directory" command will cause a stack overflow error (system error 28). This has been fixed in AD 1.0.4.
TRASH ALIAS, FILE SHARE
This is purely a conflict between TrashAlias and FileShare. It occurs in the presence of any other INIT, or no othter INITs. If you drag an item to the trash and empty it, the watch cursor will come up and never go away. The solution is to turn off TrashAlias.
ON CUE II, AD (any version)
Using OnCue II, undet the "Configure..." dialog, inserting a folder into the OnCue II menu as an "OnCue II Folder" can cause a bus error. We have investiagted the problem and believe that it is not caused by AutoDoubler. We are in contact with ICOM to resolve the problem.
AlarmsClock (any version)
Alarms clock has a bug in it that causes the system to freeze when AutoDoubler is installed.
